\section{Route Class Reference}
\label{a00125}\index{BPMVE\_\-XPDL\_\-Library::Route@{BPMVE\_\-XPDL\_\-Library::Route}}


7.6.2. \doxyref{Route}{p.}{a00125} \doxyref{Activity}{p.}{a00002} The \doxyref{Route}{p.}{a00125} \doxyref{Activity}{p.}{a00002} is a ―dummy‖ \doxyref{Activity}{p.}{a00002} that permits the explicit expression of the behavior of diverging (split) OR converging (join) sequence flow (in BPMN, the split AND join behavior for non-\/gateway activities is always the same: joins are always Exclusive AND splits are always Inclusive).  




Inheritance diagram for Route:

Collaboration diagram for Route:\subsection*{Properties}
\begin{DoxyCompactItemize}
\item 
GatewayTypeEnum {\bf GatewayType}\hspace{0.3cm}{\ttfamily  [get, set]}
\item 
ExclusiveTypeEnum {\bf ExclusiveType}\hspace{0.3cm}{\ttfamily  [get, set]}
\item 
bool {\bf IsInstantiate}\hspace{0.3cm}{\ttfamily  [get, set]}
\item 
bool {\bf IsMarkerVisible}\hspace{0.3cm}{\ttfamily  [get, set]}
\item 
string {\bf IncomingCondiiton}\hspace{0.3cm}{\ttfamily  [get, set]}
\item 
string {\bf OutgoingCondition}\hspace{0.3cm}{\ttfamily  [get, set]}
\end{DoxyCompactItemize}


\subsection{Detailed Description}


Definition at line 14 of file Route.cs.



\subsection{Property Documentation}
\index{BPMVE\_\-XPDL\_\-Library::Route@{BPMVE\_\-XPDL\_\-Library::Route}!GatewayType@{GatewayType}}
\index{GatewayType@{GatewayType}!BPMVE_XPDL_Library::Route@{BPMVE\_\-XPDL\_\-Library::Route}}
\subsubsection[{GatewayType}]{\setlength{\rightskip}{0pt plus 5cm}GatewayTypeEnum GatewayType\hspace{0.3cm}{\ttfamily  [get, set]}}\label{a00125_a5f7c16b3667fc80eafc1452a5563b2fc}


Specifies the split / join behavior of his gateway activity. Note that the enumerations XOR, OR AND AND are deprecated AND replaced by the new enumerations Exclusive, Inclusive AND Parallel respectively. It is recommended that modellers are capable of reading deprecated values but always write the new enumerations. When used for BPMN gateways, the GatewayType MUST be specified. 



Definition at line 24 of file Route.cs.

\index{BPMVE\_\-XPDL\_\-Library::Route@{BPMVE\_\-XPDL\_\-Library::Route}!ExclusiveType@{ExclusiveType}}
\index{ExclusiveType@{ExclusiveType}!BPMVE_XPDL_Library::Route@{BPMVE\_\-XPDL\_\-Library::Route}}
\subsubsection[{ExclusiveType}]{\setlength{\rightskip}{0pt plus 5cm}ExclusiveTypeEnum ExclusiveType\hspace{0.3cm}{\ttfamily  [get, set]}}\label{a00125_acd4dc74bcd1a077944b9b640bd14a58e}


For BPMN ―Exclusive‖ gateways this attribute MAY be specified when the GatewayType is specified as ―Exclusive‖, this attribute is used To specify whether the gateway is an Exclusive Data-\/Based gateway (default) OR an Exclusive Event-\/Based gateway. For Other gateway types, this attribute MUST NOT be specified. 



Definition at line 33 of file Route.cs.

\index{BPMVE\_\-XPDL\_\-Library::Route@{BPMVE\_\-XPDL\_\-Library::Route}!IsInstantiate@{IsInstantiate}}
\index{IsInstantiate@{IsInstantiate}!BPMVE_XPDL_Library::Route@{BPMVE\_\-XPDL\_\-Library::Route}}
\subsubsection[{IsInstantiate}]{\setlength{\rightskip}{0pt plus 5cm}bool IsInstantiate\hspace{0.3cm}{\ttfamily  [get, set]}}\label{a00125_a9267d456358800cee4f32208396ca6fb}


Exclusive Event-\/Based Gateways can be defined as the instantiation mechanism for the Process with the Instantiate attribute. This attribute MAY be set To true if the Gateway is the first element After the Start \doxyref{Event}{p.}{a00058} OR a starting Gateway if there is no Start \doxyref{Event}{p.}{a00058} (i.e., there are no incoming Sequence Flow). 



Definition at line 42 of file Route.cs.

\index{BPMVE\_\-XPDL\_\-Library::Route@{BPMVE\_\-XPDL\_\-Library::Route}!IsMarkerVisible@{IsMarkerVisible}}
\index{IsMarkerVisible@{IsMarkerVisible}!BPMVE_XPDL_Library::Route@{BPMVE\_\-XPDL\_\-Library::Route}}
\subsubsection[{IsMarkerVisible}]{\setlength{\rightskip}{0pt plus 5cm}bool IsMarkerVisible\hspace{0.3cm}{\ttfamily  [get, set]}}\label{a00125_a6e4622c3f72e908e7198e48224a977eb}


This attribute determines if the XOR Marker is displayed in the center of the Gateway Diamond (an ―X‖). The marker is displayed if the attribute is True AND it is not displayed if the attribute is False. By default, the marker is not displayed. 



Definition at line 50 of file Route.cs.

\index{BPMVE\_\-XPDL\_\-Library::Route@{BPMVE\_\-XPDL\_\-Library::Route}!IncomingCondiiton@{IncomingCondiiton}}
\index{IncomingCondiiton@{IncomingCondiiton}!BPMVE_XPDL_Library::Route@{BPMVE\_\-XPDL\_\-Library::Route}}
\subsubsection[{IncomingCondiiton}]{\setlength{\rightskip}{0pt plus 5cm}string IncomingCondiiton\hspace{0.3cm}{\ttfamily  [get, set]}}\label{a00125_ab9bfe2f1f3b192d8de13bfdd7dc74f4c}


For a Complex Gateway, if there are Multiple incoming Sequence Flow, an IncomingCondition expression MUST be set by the modeler. This will consist of an expression that can reference Sequence Flow names AND/OR Process Properties (Data). 



Definition at line 58 of file Route.cs.

\index{BPMVE\_\-XPDL\_\-Library::Route@{BPMVE\_\-XPDL\_\-Library::Route}!OutgoingCondition@{OutgoingCondition}}
\index{OutgoingCondition@{OutgoingCondition}!BPMVE_XPDL_Library::Route@{BPMVE\_\-XPDL\_\-Library::Route}}
\subsubsection[{OutgoingCondition}]{\setlength{\rightskip}{0pt plus 5cm}string OutgoingCondition\hspace{0.3cm}{\ttfamily  [get, set]}}\label{a00125_a0f39a38618218bbc851d8bf197a5754a}


For a Complex Gateway, if there are Multiple outgoing Sequence Flow, an OutgoingCondition expression MUST be set by the modeler. This will consist of an expression that can reference (outgoing) Sequence Flow Ids AND/OR Process Properties (Data). 



Definition at line 66 of file Route.cs.

